home *** CD-ROM | disk | FTP | other *** search
/ IRIX Base Documentation 2002 November / SGI IRIX Base Documentation 2002 November.iso / usr / share / catman / p_man / cat3n / t_accept.z / t_accept
Encoding:
Text File  |  2002-10-03  |  15.2 KB  |  199 lines
  1.  
  2.  
  3.  
  4. tttt____aaaacccccccceeeepppptttt((((3333NNNN))))                                                      tttt____aaaacccccccceeeepppptttt((((3333NNNN))))
  5.  
  6.  
  7.  
  8. NNNNAAAAMMMMEEEE
  9.      _tttt______aaaa_cccc_cccc_eeee_pppp_tttt - accept a connect request
  10.  
  11. SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
  12.      _####_iiii_ffff_dddd_eeee_ffff ______XXXX_OOOO_PPPP_EEEE_NNNN______SSSS_OOOO_UUUU_RRRR_CCCC_EEEE
  13.      _####_iiii_nnnn_cccc_llll_uuuu_dddd_eeee _<<<<_xxxx_tttt_iiii_...._hhhh_>>>>
  14.      _####_eeee_llll_ssss_eeee
  15.      _####_iiii_nnnn_cccc_llll_uuuu_dddd_eeee _<<<<_tttt_iiii_uuuu_ssss_eeee_rrrr_...._hhhh_>>>>
  16.      _####_eeee_nnnn_dddd_iiii_ffff
  17.  
  18.      _iiii_nnnn_tttt _tttt______aaaa_cccc_cccc_eeee_pppp_tttt_(((( _iiii_nnnn_tttt _ffff_dddd_,,,, _iiii_nnnn_tttt _rrrr_eeee_ssss_ffff_dddd_,,,, _ssss_tttt_rrrr_uuuu_cccc_tttt _tttt______cccc_aaaa_llll_llll _****_cccc_aaaa_llll_llll_))))_;;;;
  19.  
  20. DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
  21.      This function is issued by a transport user to accept a connect request.
  22.      _ffff_dddd identifies the local transport endpoint where the connect indication
  23.      arrived, _rrrr_eeee_ssss_ffff_dddd specifies the local transport endpoint where the
  24.      connection is to be established, and _cccc_aaaa_llll_llll contains information required
  25.      by the transport provider to complete the connection.  _cccc_aaaa_llll_llll points to a
  26.      _tttt______cccc_aaaa_llll_llll structure that contains the following members:
  27.  
  28.           _ssss_tttt_rrrr_uuuu_cccc_tttt _nnnn_eeee_tttt_bbbb_uuuu_ffff _aaaa_dddd_dddd_rrrr_;;;;
  29.           _ssss_tttt_rrrr_uuuu_cccc_tttt _nnnn_eeee_tttt_bbbb_uuuu_ffff _oooo_pppp_tttt_;;;;
  30.           _ssss_tttt_rrrr_uuuu_cccc_tttt _nnnn_eeee_tttt_bbbb_uuuu_ffff _uuuu_dddd_aaaa_tttt_aaaa_;;;;
  31.           _iiii_nnnn_tttt _ssss_eeee_qqqq_uuuu_eeee_nnnn_cccc_eeee_;;;;
  32.  
  33.      _nnnn_eeee_tttt_bbbb_uuuu_ffff is described in _iiii_nnnn_tttt_rrrr_oooo(3N).  In _cccc_aaaa_llll_llll, _aaaa_dddd_dddd_rrrr is the address of the
  34.      caller, _oooo_pppp_tttt indicates any protocol-specific parameters associated with
  35.      the connection, _uuuu_dddd_aaaa_tttt_aaaa points to any user data to be returned to the
  36.      caller, and _ssss_eeee_qqqq_uuuu_eeee_nnnn_cccc_eeee is the value returned by _tttt______llll_iiii_ssss_tttt_eeee_nnnn that uniquely
  37.      associates the response with a previously received connect indication.
  38.  
  39.      A transport user may accept a connection on either the same, or on a
  40.      different, local transport endpoint from the one on which the connect
  41.      indication arrived.  If the same endpoint is specified (that is,
  42.      _rrrr_eeee_ssss_ffff_dddd=_ffff_dddd), the connection can be accepted unless the following condition
  43.      is true:  The user has received other indications on that endpoint but
  44.      has not responded to them (with _tttt______aaaa_cccc_cccc_eeee_pppp_tttt or _tttt______ssss_nnnn_dddd_dddd_iiii_ssss).  For this
  45.      condition:
  46.  
  47.           _####_iiii_ffff_dddd_eeee_ffff ______XXXX_OOOO_PPPP_EEEE_NNNN______SSSS_OOOO_UUUU_RRRR_CCCC_EEEE
  48.                _tttt______aaaa_cccc_cccc_eeee_pppp_tttt will fail and set _tttt______eeee_rrrr_rrrr_nnnn_oooo to _TTTT_IIII_NNNN_DDDD_OOOO_UUUU_TTTT.
  49.           _####_eeee_llll_ssss_eeee
  50.                _tttt______aaaa_cccc_cccc_eeee_pppp_tttt will fail and set _tttt______eeee_rrrr_rrrr_nnnn_oooo to _TTTT_BBBB_AAAA_DDDD_FFFF.
  51.           _####_eeee_nnnn_dddd_iiii_ffff
  52.  
  53.      If a different transport endpoint is specified (_rrrr_eeee_ssss_ffff_dddd!=_ffff_dddd), the endpoint
  54.      must be bound to a protocol address and must be in the _TTTT______IIII_DDDD_LLLL_EEEE state [see
  55.      _tttt______gggg_eeee_tttt_ssss_tttt_aaaa_tttt_eeee(3N)] before the _tttt______aaaa_cccc_cccc_eeee_pppp_tttt is issued.
  56.  
  57.      For both types of endpoints, _tttt______aaaa_cccc_cccc_eeee_pppp_tttt will fail and set _tttt______eeee_rrrr_rrrr_nnnn_oooo to _TTTT_LLLL_OOOO_OOOO_KKKK
  58.      if there are indications (for example, a connect or disconnect) waiting
  59.      to be received on that endpoint.
  60.  
  61.  
  62.  
  63.                                                                         PPPPaaaaggggeeee 1111
  64.  
  65.  
  66.  
  67.  
  68.  
  69.  
  70. tttt____aaaacccccccceeeepppptttt((((3333NNNN))))                                                      tttt____aaaacccccccceeeepppptttt((((3333NNNN))))
  71.  
  72.  
  73.  
  74.      The values of parameters specified by _oooo_pppp_tttt and the syntax of those values
  75.      are protocol specific.  The _uuuu_dddd_aaaa_tttt_aaaa argument enables the called transport
  76.      user to send user data to the caller and the amount of user data must not
  77.      exceed the limits supported by the transport provider as returned in the
  78.      _cccc_oooo_nnnn_nnnn_eeee_cccc_tttt field of the _iiii_nnnn_ffff_oooo argument of _tttt______oooo_pppp_eeee_nnnn or _tttt______gggg_eeee_tttt_iiii_nnnn_ffff_oooo.  If the _llll_eeee_nnnn
  79.      [see _nnnn_eeee_tttt_bbbb_uuuu_ffff in _iiii_nnnn_tttt_rrrr_oooo(3N)] field of _uuuu_dddd_aaaa_tttt_aaaa is zero, no data will be sent to
  80.      the caller.
  81.  
  82.      This function resides within both the X/Open compliant _llll_iiii_bbbb_xxxx_nnnn_eeee_tttt and the
  83.      SVR4 compliant _llll_iiii_bbbb_nnnn_ssss_llll Network Services libraries.  Network Services
  84.      applications which require X/Open compliance must link-load with _----_llll_xxxx_nnnn_eeee_tttt.
  85.      Network Services applications which require SVR4 compliance must link-
  86.      load with _----_llll_nnnn_ssss_llll.
  87.  
  88.      On failure, _tttt______eeee_rrrr_rrrr_nnnn_oooo may be set to one of the following:
  89.  
  90.      _TTTT_BBBB_AAAA_DDDD_FFFF              The specified file descriptor does not refer to a
  91.                         transport endpoint, or the user is invalidly accepting
  92.                         a connection on the same transport endpoint on which
  93.                         the connect indication arrived.
  94.  
  95.      _TTTT_OOOO_UUUU_TTTT_SSSS_TTTT_AAAA_TTTT_EEEE          The function was issued in the wrong sequence on the
  96.                         transport endpoint referenced by _ffff_dddd, or the transport
  97.                         endpoint referred to by _rrrr_eeee_ssss_ffff_dddd is not in the _TTTT______IIII_DDDD_LLLL_EEEE
  98.                         state.
  99.  
  100.      _TTTT_AAAA_CCCC_CCCC_EEEE_SSSS             The user does not have permission to accept a
  101.                         connection on the responding transport endpoint or use
  102.                         the specified options.
  103.  
  104.      _TTTT_BBBB_AAAA_DDDD_OOOO_PPPP_TTTT            The specified options were in an incorrect format or
  105.                         contained invalid information.
  106.  
  107.      _TTTT_BBBB_AAAA_DDDD_DDDD_AAAA_TTTT_AAAA           The amount of user data specified was not within the
  108.                         bounds supported by the transport provider as returned
  109.                         in the _cccc_oooo_nnnn_nnnn_eeee_cccc_tttt field of the _iiii_nnnn_ffff_oooo argument of _tttt______oooo_pppp_eeee_nnnn or
  110.                         _tttt______gggg_eeee_tttt_iiii_nnnn_ffff_oooo.
  111.  
  112.      _TTTT_BBBB_AAAA_DDDD_AAAA_DDDD_DDDD_RRRR           If ______XXXX_OOOO_PPPP_EEEE_NNNN______SSSS_OOOO_UUUU_RRRR_CCCC_EEEE is defined, _TTTT_BBBB_AAAA_DDDD_AAAA_DDDD_DDDD_RRRR will be returned
  113.                         because the specified protocol address was in an
  114.                         incorrect format or contained illegal information.
  115.  
  116.      _TTTT_BBBB_AAAA_DDDD_SSSS_EEEE_QQQQ            An invalid sequence number was specified.
  117.  
  118.      _TTTT_FFFF_LLLL_OOOO_WWWW              An _eeee_rrrr_rrrr_nnnn_oooo of EAGAIN was returned from the ioctl() call
  119.                         when trying to send the connection response packet.
  120.                         When this happens, _tttt______eeee_rrrr_rrrr_nnnn_oooo is set to _TTTT_FFFF_LLLL_OOOO_WWWW.
  121.  
  122.      _TTTT_LLLL_OOOO_OOOO_KKKK              An asynchronous event has occurred on the transport
  123.                         endpoint referenced by _ffff_dddd and requires immediate
  124.                         attention.
  125.  
  126.  
  127.  
  128.  
  129.                                                                         PPPPaaaaggggeeee 2222
  130.  
  131.  
  132.  
  133.  
  134.  
  135.  
  136. tttt____aaaacccccccceeeepppptttt((((3333NNNN))))                                                      tttt____aaaacccccccceeeepppptttt((((3333NNNN))))
  137.  
  138.  
  139.  
  140.      _TTTT_NNNN_OOOO_TTTT_SSSS_UUUU_PPPP_PPPP_OOOO_RRRR_TTTT        This function is not supported by the underlying
  141.                         transport provider.
  142.  
  143.      _TTTT_SSSS_YYYY_SSSS_EEEE_RRRR_RRRR            A system error has occurred during execution of this
  144.                         function.
  145.  
  146.      _TTTT_IIII_NNNN_DDDD_OOOO_UUUU_TTTT            If ______XXXX_OOOO_PPPP_EEEE_NNNN______SSSS_OOOO_UUUU_RRRR_CCCC_EEEE is defined, _TTTT_IIII_NNNN_DDDD_OOOO_UUUU_TTTT will be returned
  147.                         because the function was called with _ffff_dddd=_rrrr_eeee_ssss_ffff_dddd but
  148.                         there are outstanding connection indications on the
  149.                         endpoint.  Those other connection indications must be
  150.                         handled either by rejecting them via _tttt______ssss_nnnn_dddd_dddd_iiii_ssss(3N) or
  151.                         accepting them on a different endpoint via
  152.                         _tttt______aaaa_cccc_cccc_eeee_pppp_tttt(3N).
  153.  
  154.      _TTTT_PPPP_RRRR_IIII_VVVV_MMMM_IIII_SSSS_MMMM_AAAA_TTTT_CCCC_HHHH      If ______XXXX_OOOO_PPPP_EEEE_NNNN______SSSS_OOOO_UUUU_RRRR_CCCC_EEEE is defined, _TTTT_PPPP_RRRR_IIII_VVVV_MMMM_IIII_SSSS_MMMM_AAAA_TTTT_CCCC_HHHH will be
  155.                         returned because the file descriptors _ffff_dddd and _rrrr_eeee_ssss_ffff_dddd do
  156.                         not refer to the same transport provider.
  157.  
  158.      _TTTT_RRRR_EEEE_SSSS_QQQQ_LLLL_EEEE_NNNN           If ______XXXX_OOOO_PPPP_EEEE_NNNN______SSSS_OOOO_UUUU_RRRR_CCCC_EEEE is defined, _TTTT_RRRR_EEEE_SSSS_QQQQ_LLLL_EEEE_NNNN will be returned
  159.                         because the endpoint referenced by _rrrr_eeee_ssss_ffff_dddd (where _rrrr_eeee_ssss_ffff_dddd
  160.                         != _ffff_dddd) was bound to a protocol address with a _qqqq_llll_eeee_nnnn
  161.                         that is greater than zero.
  162.  
  163.      _TTTT_PPPP_RRRR_OOOO_TTTT_OOOO             If ______XXXX_OOOO_PPPP_EEEE_NNNN______SSSS_OOOO_UUUU_RRRR_CCCC_EEEE is defined, _TTTT_PPPP_RRRR_OOOO_TTTT_OOOO will be returned
  164.                         because a communication problem has been detected
  165.                         between XTI and the transport provider for whicjh
  166.                         there is no other suitable XTI (_tttt______eeee_rrrr_rrrr_nnnn_oooo).
  167.  
  168.      _TTTT_RRRR_EEEE_SSSS_AAAA_DDDD_DDDD_RRRR           If ______XXXX_OOOO_PPPP_EEEE_NNNN______SSSS_OOOO_UUUU_RRRR_CCCC_EEEE is defined, _TTTT_RRRR_EEEE_SSSS_AAAA_DDDD_DDDD_RRRR will be returned
  169.                         because this transport provider requires both _ffff_dddd and
  170.                         _rrrr_eeee_ssss_ffff_dddd to be bound to the same address.  This error
  171.                         results if they are not.
  172.  
  173. SSSSEEEEEEEE AAAALLLLSSSSOOOO
  174.      _iiii_nnnn_tttt_rrrr_oooo(3N), _tttt______cccc_oooo_nnnn_nnnn_eeee_cccc_tttt(3N), _tttt______gggg_eeee_tttt_ssss_tttt_aaaa_tttt_eeee(3N), _tttt______llll_iiii_ssss_tttt_eeee_nnnn(3N), _tttt______oooo_pppp_eeee_nnnn(3N),
  175.      _tttt______oooo_pppp_tttt_mmmm_gggg_mmmm_tttt(3N) _tttt______rrrr_cccc_vvvv_cccc_oooo_nnnn_nnnn_eeee_cccc_tttt(3N)
  176.  
  177. DDDDIIIIAAAAGGGGNNNNOOOOSSSSTTTTIIIICCCCSSSS
  178.      Upon successful completion, a value of 0 is returned.  Otherwise, a value
  179.      of -1 is returned and _tttt______eeee_rrrr_rrrr_nnnn_oooo is set to indicate the error.
  180.  
  181.  
  182.  
  183.  
  184.  
  185.  
  186.  
  187.  
  188.  
  189.  
  190.  
  191.  
  192.  
  193.  
  194.  
  195.                                                                         PPPPaaaaggggeeee 3333
  196.  
  197.  
  198.  
  199.